Run In Separate Process

During a macro execution no other macro can start.  This is not convenient for macros that can take very long to finish (for example, FTP download).  In such case there is an option to start time consuming macro in separate process so that it doesn't block other macros from starting.  In addition, this option allows user to run macros concurrently or run them as a service or on other user's account. 

Starting macro in separate process means, that a new executable (_prog.exe) to run the macro is loaded to computer memory and the macro execution continues within the executable.  When macro execution is finished, the executable is released from the computer memory again.  There are three ways how the program can be started:

1. Normal (as currently logged user) - this is the default option.

2. Run as different user - this option allows user to start macro on other user's account.  It is necessary to specify user name and password (and, optionally, domain).  In addition, this option requires specific user rights to be set in Windows: Act as part of the operating system (SE_TCB_NAME), Bypass traverse checking (SE_CHANGE_NOTIFY_NAME) , Replace a process level token (SE_ASSIGNPRIMARYTOKEN_NAME), Increase quotas (SE_INCREASE_QUOTA_NAME). 
There is "WhoAmI.exe" utility that is part of the program distribution.  You can create simple macro consisting just from <execappex>("whoami.exe","","",0,0) command.  When the macro is started a WhoAmI.exe dialog box shows user name of the account under which the WhoAmI.exe program was started.  This can be used to make sure the macro is started on right account. 

3. Run as system service - this option allows user to run macro as a system service.  In this case, the WhoAmI.exe sample (see #2 above) shows "SYSTEM".

This option is available in macro definition view, in "Settings" tab.